-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMN-799 Add scaffold for purpose-platformstate-writer #969
Conversation
…lient-assertion-validation
…atalog-platformstate-writer-v1
…com/pagopa/interop-be-monorepo into IMN-522_client-assertion-validation
…atalog-platformstate-writer-v1
…lient-assertion-validation
…se-platformstate-writer-scaffold
…atalog-platformstate-writer-v1
…hub.com/pagopa/interop-be-monorepo into IMN-797_catalog-platformstate-writer-v1
…lient-assertion-validation
…se-platformstate-writer-scaffold
} from "pagopa-interop-models"; | ||
import { config } from "./config/config.js"; | ||
|
||
export const writePlatformPurposeEntry = async ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since there write, read and delete are almost identical to the ones here would it be beneficial to declare these as generics and move to commons
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving to commons is being planned, but I wouldn't turn those into functions with generics, because it doesn't seem a straightforward operation, considering the differences between those entries.
Closes IMN-799
Merge after #956
This pull request is for adding the scaffold of the new
purpose-platformstate-writer
package.